Ensure the mini-cart block uses the block.json metadata file as the canonical way to register the block type with both PHP (server-side) and JavaScript (client-side) as this has been the recommended approach for registering blocks since WordPress 5.8.

The benefits of this change are highlighted in this post, which includes:

• The block definition allows code sharing between JavaScript, PHP, and other languages when processing block types stored as JSON, and registering blocks with the block.json metadata file provides multiple benefits on top of it.

• From a performance perspective, when themes support lazy loading assets, blocks registered with block.json will have their asset enqueuing optimized out of the box. The frontend CSS and JavaScript assets listed in the style or script properties will only be enqueued when the block is present on the page, resulting in reduced page sizes.

• Furthermore, because the Block Type REST API Endpoint can only list blocks registered on the server, registering blocks server-side is recommended; using the block.json file simplifies this registration.

• The WordPress Plugins Directory can detect block.json files, highlight blocks included in plugins, and extract their metadata.

Testing

User Facing Testing

1. Create a new post
2. Make sure the mini-cart block is available for insertion
3. Insert the block, make changes to its settings and save
4. On the frontend, make sure everything works as expected: you can add/remove products from the cart and the style changes made in the editor are visible on the frontend.

WooCommerce Visibility

• WooCommerce Core
• Feature plugin
• Experimental

Changelog

Modernize the block registration for the Mini Cart block.